Method and device for hosting application by access node

ABSTRACT

A method and device for hosting an application by an access node which provides network access to a terminal in a mobile communication system are provided. The method includes receiving a request packet for a service request from a user application of a mobile terminal, delivering the request packet to an application included in the access node, if a destination of the request packet corresponds to the application of the access node, providing a service to the user application of the mobile terminal through the application, and delivering the request packet to a corresponding public application on an external network, if the application corresponding to the destination of the request packet does not exist in the access node.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a U.S. National Stage application under 35 U.S.C.§371 of an International application filed on Nov. 7, 2013 and assignedapplication number PCT/KR2013/010076, which claimed the benefit of aKorean patent application filed on Nov. 8, 2012 in the KoreanIntellectual Property Office and assigned Serial number 10-2012-0126013,the entire disclosure of which is hereby incorporated by reference.

TECHNICAL FIELD

The present disclosure relates to a wireless communication system. Moreparticularly, the present disclosure relates to a method and apparatusfor hosting an application service by an access node in a wirelesscommunication system.

BACKGROUND

With the rapidly increasing use of portable computing devices such assmartphones, tablet computers, and the like, various Internetapplication services have been provided over cellular mobilecommunication networks. In a cellular mobile communication system, ageneral access node that is in charge of a wireless connection with amobile terminal, is configured to serve as a simple bit-pipe which uponreceiving an Internet service request from the terminal, delivers theInternet service request to an Application Server (AS) of the Internetand delivers a response from the AS to the terminal.

Existing platforms as described above have difficulties in hostingvarious applications and providing application differentiation anddifferent levels of Quality of Service (QoS). Moreover, for theseexisting platforms, it is not easy to add new additional servicescorresponding to changes in technologies and to use resources of anaccess network in providing various application services.

The above information is presented as background information only toassist with an understanding of the present disclosure. No determinationhas been made, and no assertion is made, as to whether any of the abovemight be applicable as prior art with regard to the present disclosure.

SUMMARY

Aspects of the present disclosure are to address at least theabove-mentioned problems and/or disadvantages and to provide at leastthe advantages described below. Accordingly, an aspect of the presentdisclosure is to provide a method and apparatus for hosting anapplication service by an access node in a wireless communicationsystem.

Another aspect of the present disclosure is to provide a method anddevice for hosting applications by an access node in a cellular mobilecommunication network.

Another aspect of the present disclosure is to provide a method anddevice for hosting various applications and using information of anaccess network by an access node.

Another aspect of the present disclosure is to provide a method anddevice for filtering a service request of a user with a base stationapplication when necessary.

Another aspect of the present disclosure is to provide a method anddevice for directly providing an Internet service by a base station to aterminal based on interworking between an access network and a basestation application.

In accordance with an aspect of the present disclosure, a method forhosting an application by an access node which provides network accessto a terminal in a mobile communication system is provided. The methodincludes receiving a request packet for a service request from a userapplication of a mobile terminal, delivering the request packet to anapplication included in the access node, if a destination of the requestpacket corresponds to the application of the access node, providing aservice to the user application of the mobile terminal through theapplication, and delivering the request packet to a corresponding publicapplication on an external network, if the application corresponding tothe destination of the request packet does not exist in the access node.

In accordance with another aspect of the present disclosure, an accessnode device which provides network access to a terminal and providesapplication hosting in a mobile communication system is provided. Theaccess node device includes a forwarding unit configured to identify adestination of a request packet, upon receiving the request packet for aservice request from a user application of a mobile terminal, to deliverthe request packet to an application included in the access node, if adestination of the request packet corresponds to the application of theaccess node, and to deliver the request packet to a corresponding publicapplication on an external network, if the application corresponding tothe destination of the request packet does not exist in the access node,and an application executing unit configured to provide a service to theuser application of the mobile terminal through the application.

Other aspects, advantages, and salient features of the disclosure willbecome apparent to those skilled in the art from the following detaileddescription, which, taken in conjunction with the annexed drawings,discloses various embodiments of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 schematically illustrates a structure of a system for providingan Internet service through an access network according to an embodimentof the present disclosure;

FIG. 2 schematically illustrates a structure of a system including abase station system according to an embodiment of the presentdisclosure;

FIG. 3 illustrates a structure of an access node according to anembodiment of the present disclosure;

FIG. 4 illustrates a call flow of a scenario where a terminal receives aservice from an edge application or a public application according to anembodiment of the present disclosure;

FIG. 5 illustrates a call flow of a scenario where a terminal receivesaccess network information according to an embodiment of the presentdisclosure;

FIG. 6 illustrates a detailed structure of a filtering and forwardingunit according to an embodiment of the present disclosure; and

FIGS. 7, 8 and 9 illustrate operations corresponding to servicescenarios according to various embodiments of the present disclosure.

Throughout the drawings, it should be noted that like reference numbersare used to depict the same or similar elements, features, andstructures.

DETAILED DESCRIPTION

The following description with reference to the accompanying drawings isprovided to assist in a comprehensive understanding of variousembodiments of the present disclosure as defined by the claims and theirequivalents. It includes various specific details to assist in thatunderstanding but these are to be regarded as merely exemplary.Accordingly, those of ordinary skill in the art will recognize thatvarious changes and modifications of the various embodiments describedherein can be made without departing from the scope and spirit of thepresent disclosure. In addition, descriptions of well-known functionsand constructions may be omitted for clarity and conciseness.

The terms and words used in the following description and claims are notlimited to the bibliographical meanings, but, are merely used by theinventor to enable a clear and consistent understanding of the presentdisclosure. Accordingly, it should be apparent to those skilled in theart that the following description of various embodiments of the presentdisclosure is provided for illustration purpose only and not for thepurpose of limiting the present disclosure as defined by the appendedclaims and their equivalents.

It is to be understood that the singular forms “a,” “an,” and “the”include plural referents unless the context clearly dictates otherwise.Thus, for example, reference to “a component surface” includes referenceto one or more of such surfaces.

FIGS. 1 through 9, discussed below, and the various embodiments used todescribe the principles of the present disclosure in this patentdocument are by way of illustration only and should not be construed inany way that would limit the scope of the disclosure. Those skilled inthe art will understand that the principles of the present disclosuremay be implemented in any suitably arranged communications system. Theterms used to describe various embodiments are exemplary. It should beunderstood that these are provided to merely aid the understanding ofthe description, and that their use and definitions in no way limit thescope of the present disclosure. Terms first, second, and the like areused to differentiate between objects having the same terminology andare in no way intended to represent a chronological order, unless whereexplicitly stated otherwise. A set is defined as a non-empty setincluding at least one element.

A Mobile Station (MS), a User Equipment (UE), a smartphone, or a mobiledevice such as a tablet computer having a communication module mountedthereon is configured to connect to the Internet over an access networkof a cellular wireless communication system such as 3^(rd) GenerationPartnership Project (3GPP) Long-Term Evolution (LTE).

FIG. 1 schematically illustrates a structure of a system that providesan Internet Service over an access network according to an embodiment ofthe present disclosure.

Referring to FIG. 1, a system is illustrated, in which a mobile terminal100 may include a communication module capable of cellular wirelesscommunication, and may also include one or more applications 102 thatneed connection with an application 122 executed in an ApplicationServer (AS) 124 on a public network 120 such as the Internet or anothernetwork that provides connection with a wireless network. Herein, forconvenience of explanation, the application 102 executed on a mobileterminal will be referred to as a “User Application” and the application122 executed on the Internet or the external another network (or the AS)120 will be referred to as a “Public Application.”

The mobile terminal 100 connects to the Internet or the external network120 over an operator network 110 that includes an Access Network (AN)112 and a Core Network (CN) 118. The AN 112 includes an access node 114,such as a Base Station (BS), a Node B, or an Evolved Node B (eNB), whichprovides a network access point for the mobile terminal 100, andincludes at least one data service node that provide connection with theexternal network such as the Internet 120.

The access node 114 includes a BaseBand Unit (BBU) 116 that is in chargeof data and signal processing for a mobile communication network. Aservice request from the user application 102 is delivered to the publicapplication 122 of the Internet or external network 120 over theoperator network 110, and the public application 122 then providescontent or information to the mobile terminal 100 in response to thereceived service request. The AN 112 and the CN 118 of the operatornetwork 110 process the service request and user traffic for the mobileterminal 100 according to a policy and a rule based on subscriberinformation.

Various embodiments of the present disclosure described below relate todirectly providing an application-based service to a mobile terminal 100by an access node 114 in an AN 112, in place of a service on theInternet or external network 120.

FIG. 2 schematically illustrates a structure of a system including a BSsystem according to an embodiment of the present disclosure.

Referring to FIG. 2, a system is illustrated, in which a mobile terminal200 that executes a user application 202 connects to an AN of anoperator network through an access node 210 which connects to a pubicapplication 232 included in an AS 234 of the Internet or externalnetwork 230 through a CN 220. The access node 210 refers to a BS thatprovides connection to a mobile communication network to the mobileterminal 200, and may be a Node B in a 3G network and an eNB in an LTEnetwork.

The AN 210 includes a BBU 212 that is in charge of general data andsignal processing for a mobile communication network, and may alsoinclude a filter unit 214 for identifying and processing data of aparticular application packet and a network information handler 216 forobtaining information about an AN (hereinafter, referred to as “accessnetwork information”) when necessary. The access node 210 hosts anapplication 218 for a user service, and herein, the application 218executed in the access node 210 will be referred to as an “EdgeApplication.” The edge application 218 may provide a service to a userby using dynamically changing AN information, and, when necessary, mayprovide a service by interworking with the public application 232 of theInternet or external network 230 through a CN.

The user application 202 of the mobile terminal 200 sends a request forparticular AN information to the access node 210 or sends a servicerequest to the edge application 218 or the public application 232. Ifthe user application 202 directly requests the AN information, acorresponding service request is filtered by the filter unit 214 of theBBU 212 and delivered to the network information handler 216 which thentransmits the AN information to the user application 202 of the mobileterminal 200 in response to the service request. If the user application202 of the mobile terminal 200 sends a service request to the edgeapplication 218 or the particular public application 232, the servicerequest is filtered by the filter unit 214 of the BBU 212 and deliveredto the edge application 218 which then provides a service directly orusing information or content from the public application 232, inresponse to the service request.

Various types of services may be provided through the edge application218 hosted in the access node 210, and the following examples are ofpossible service scenarios.

In a first service scenario, a user application of a terminal sends aservice request to an edge application of an access node, and the edgeapplication directly delivers content or information to the mobileterminal in response to the received service request. This type ofservice may be used to serve local information such as a local weatheror to provide traffic information of an AN to an authorized mobileterminal This service causes no service traffic to a CN of an operatornetwork, reducing the usage of backhaul.

In a second scenario, the user application sends a service request tothe edge application which then handles the service process directly orthrough communication with the public application. In this case, theedge application may directly send a response to the service request tothe user application, but when necessary, may communicate with thepublic application to obtain desired information or content. An exampleof this type of scenario is a real-time game, in which the edgeapplication directly delivers information, which may be directlyresponded by the edge application, to the user without communicatingwith the public application, and obtains additional information, whichis not included in the edge application, by communicating with thepublic application of the Internet or external network and provides aservice to the user by using the obtained information.

In a third service scenario, the edge application operates transparentlybetween the user application and the public application, and the userapplication is regarded as receiving a service by communicating with thepublic application, without noticing that the edge application existsbetween the user application and the public application. An example ofthis type of service is an edge cache operating transparently, in whichthe edge application operates as an edge cache to reduce a response timeto a user request and a content transmission time.

Although the foregoing service scenarios have been described as examplesherein, other types of services may also be provided through the edgeapplication in other various embodiments of the present disclosure.

A detailed description will now be made of a structure of an access nodeassociated with a service scenario in which a request for AN informationand a service request are processed.

FIG. 3 illustrates a structure of an access node according to anembodiment of the present disclosure. Referring to FIG. 3, an example ofan LTE BS is illustrated.

Referring to FIG. 3, a system is illustrated, in which a mobile terminal300 that executes a user application 302 (or a user applicationexecution block) connects to an AN of an operator network through anaccess node 310 which connects to a public application 352 on theInternet or external network 350 through a CN 340.

The access node 310 may include a communication unit 312 and anapplication hosting unit 330, in which the communication unit 312 mayinclude a BBU 314 that is in charge of general data and signalprocessing for a mobile communication network and a network informationhandler 322 for managing information about an AN, and the applicationhosting unit 330 is configured to drive one or more edge applications(or edge application execution blocks) 334 and 336. Further, theapplication hosting unit 330 includes a virtual switch 332. Herein, aPacket Data Convergence Protocol (PDCP) processor 316 and a GeneralPacket Radio Service (GPRS) Tunneling Protocol (GTP) processor 320 outof a protocol stack of the BBU 314 are illustrated, and lower layers ofthe PDCP processor 316, Radio Link Control (RLC), Medium Access Control(MAC), and Physical (PHY) are not illustrated for convenience ofexplanation.

The PDCP processor 316 is in charge of packet communication between themobile terminal 300 and the access node 310, and processes conversionand interpretation of an Internet Protocol (IP) packet. The GTPprocessor 320 delivers IP packets from the PDCP processor 316 to theInternet or external network 350 through the CN 340, or delivers IPpackets coming from the Internet or external network 350 to the PDCPprocessor 316 through the CN 340.

A Filter and Forwarding Unit (FAFU) 318 is logically located between thePDCP processor 316 and the GTP processor 320, and identifies IP packetstransmitted or received among the mobile terminal 300, the edgeapplications 334 and 336, the public application 352, and an ApplicationProgram Interface (API) module 324 according to a predetermined rule todeliver the IP packets to corresponding destinations. More specifically,the FAFU 318 identifies a packet for a network information requestand/or a service request delivered from the user application 302according to a preset rule and delivers the packet to an entity thatprocesses the corresponding request.

The packet for the network information request received from the userapplication 302 is delivered to the network information handler 322 bythe FAFU 318, and the packet for the service request received from theuser application 302 is delivered to the corresponding edge applications334 and 336. Upon receiving a packet destined to the mobile terminal 300from the public application 352 or the edge applications 334 and 336,the FAFU 318 delivers the packet to the mobile terminal 300 through thePDCP processor 316. The FAFU 318 delivers a particular packet deliveredfrom the terminal or a particular packet delivered from the edgeapplications 334 and 336 to the API module 324 of the networkinformation handler 322, and delivers a response packet delivered fromthe API module 324 to the mobile terminal 300 or the corresponding edgeapplications 334 and 336 through the PDCP processor 316.

Although the FAFU 318 has been described as an independent block that islogically located between the PDCP processor 316 and the GTP processor320 herein, the FAFU 318 may also be implemented in the PDCP processor316 or the GTP processor 320.

The network information handler 322 receives the network informationrequest through an information obtaining unit 326 by the API module 324.

In an embodiment of the present disclosure, by using a destination IPaddress included in a header of a request packet including the networkinformation request or the service request or a Universal ResourceLocator (URL) included in the header of the request packet, the FAFU 318may determine an entity for delivering the request packet. In anembodiment of the present disclosure, when the edge application 334 isconfigured in the access node 310, the destination IP address and theURL destined to the edge application 334 may be set as a filtering rulein the FAFU 318. Upon receiving the request packet including thedestination IP address and/or the URL set as the filtering rule, theFAFU 318 delivers the request packet to the edge application 334 insteadof to the CN 340.

The FAFU 318 and the edge applications 334 and 336 are connected throughIP-in-IP tunneling or Inter-Process Communication (IPC). Similarly,packet delivery between the FAFU 318 and the API module 324 of thenetwork information handler 322 may be performed through the IP-in-IPtunneling or the IPC.

Upon receiving the request packet regarding the network information, theAPI module 324 of the network information handler 322 identifies therequest packet and delivers the request packet to the informationobtaining unit 326. The information obtaining unit 326 collectsinformation about the access node 310 from the BBU 314 of the accessnode 310, an Operation and Maintenance (OAM) unit, or another functionblock or periodically or aperiodically collects network informationabout an AN, and stores and manages the collected information or networkinformation, and configures desired network information at the requestof the API module 324 and delivers the configured network information tothe API module 324. Examples of network information managed by theinformation obtaining unit 326 may include a BS identifier (ID) (or acell ID), a BS load (a cell load or a capacity indicator), a ResourceBlock (RB) usage, a BandWidth (BW) usage, channel information of anaccess subscriber, and the like.

The API module 324 configures the network information obtained from theinformation obtaining unit 326 in an IP packet format and transmits theconfigured network information to the user application 302. Morespecifically, the IP-packetized network information is delivered fromthe API module 324 to the FAFU 318 of the BBU 314, and then istransmitted to the corresponding user application 302 through acorresponding protocol stack of the BBU 314. The at least one edgeapplications 334 and 336 may transmit a request packet regarding ANinformation to the API module 324 which obtains the requested networkinformation from the information obtaining unit 326 and transmits theobtained network information to the corresponding edge applications 334and 336.

The API module 324 provides an interface for delivery of a request and aresponse in association with network information between the userapplication 302 and the edge applications 334 and 336, such thatinformation of the access node 310 is inquired and provided to themobile terminal 300 or the edge applications 334 and 336. The interfacebetween the API module 324 and the edge applications 334 and 336 may beimplemented, for example, as a web API such as Representational StateTransfer (REST), and may also be implemented in other forms such as aSoftware Development Kit (SDK), a library, or the like.

The edge applications 334 and 336 hosted in the access node 310 areexecutable on a general Information Technology (IT) server, and may beexecuted on one Operating System (OS), or may be executed on one ormultiple virtual machines if the access node 310 is logically separatedinto several virtual machines. The edge applications 334 and 336illustrated in FIG. 3 are hosted on one virtual machine, and areconnected to the BBU 314 through the virtual switch 332.

With reference to call flows illustrated in FIGS. 4 and 5, the followingdescription is of service scenarios in which an application servicerequest and an AN information request for a terminal are processed.

FIG. 4 illustrates a call flow of a scenario where a terminal receives aservice from an edge application or a public application according to anembodiment of the present disclosure.

Referring to FIG. 4, a call flow is illustrated, such that in operation402, a session is established between a mobile terminal 300 and a packetdata node (not shown) of a CN 340, which then allocates an IP address tothe mobile terminal 300 through the session establishment.

In operation 404, the mobile terminal 300 transmits a request packet fora service request generated by the user application 302, as illustratedin FIG. 3, to an access node 310. The service request generated by theuser application 302 of the mobile terminal 300 may be configured in aformat that is similar to, for example, a general Hyper Text TransferProtocol (HTTP) web content request.

The request packet transmitted from the mobile terminal 300 is filteredby the FAFU 318, as illustrated in FIG. 3, of a BBU 312 of the accessnode 310 according to a predetermined rule in operation 406, and istransmitted to a corresponding edge application identified by thefiltering in operation 408. In an embodiment, the filtering may beperformed based on a destination IP address included in a header of therequest packet. That is, upon receiving the request packet having apreset destination IP address, the FAFU 318 delivers the request packetto a corresponding edge application. In another embodiment, the FAFU 318may perform filtering by using a destination URL included in a header ofthe request packet. In operation 408, the filtered request packet istransmitted to a corresponding edge application 334 through IP-in-IPtunneling.

In operation 410, the edge application 334 sends a request for presetavailable network information to the network information handler 322 inresponse to the service request of the request packet and receives thenetwork information through API communication with the networkinformation handler 322. In an embodiment, communication for deliveringa network information request and a request result between the edgeapplication 334 and the network information handler 322 is performedthrough an interface in the form of a web API or SDK.

In operations 412 and 414, the edge application 334 provides the networkinformation corresponding to the request packet to the mobile terminal300 through the BBU 312. For example, the network information may beconfigured with one or more IP packets. If necessary, the edgeapplication 334 may send a request for information or content needed forthe mobile terminal 300 to provide a desired service to a publicapplication 352 and obtain the information or content.

If the edge application 334 cannot accept the service request of therequest packet, that is, does not provide a service requested by themobile terminal 300, the edge application 334 forwards the requestpacket to the FAFU 318 of the BBU 312 in operation 416.

The FAFU 318 of the BBU 312 transmits the request packet to thecorresponding public application 352 of the Internet 350 through the CN340 in operation 418, and the public application 352 provides therequested service to the mobile terminal 300 through the CN 340 and theBBU 312 of the access node in operation 420. If the edge application 334provides a caching service for the public application 352 in anembodiment of a detailed service, service content from the publicapplication 352 is cached (that is, stored) in the edge application 334which then provides the service content to the mobile terminal 300.

FIG. 5 illustrates a call flow of a scenario where a terminal receivesaccess network information according to an embodiment of the presentdisclosure.

Referring to FIG. 5, a call flow is illustrated, such that in operation502, a session is established between a mobile terminal 300 and a packetdata node (not shown) of a CN 340, and the CN 340 allocates an IPaddress to the mobile terminal 300 through the session establishment.

In operation 504, the mobile terminal 300 transmits a request packet forrequesting AN information generated by the user application 302, asillustrated in FIG. 3, to an access node 310. The request for the ANinformation may be configured in a format that is similar to, forexample, a general HTTP web content request.

The request packet of the mobile terminal 300 is filtered by the FAFU318, as illustrated in FIG. 3, of a BBU 312 of the access node 310according to a predetermined rule in operation 506, and is delivered bythe filtering to a network information handler 322 in operation 508. Inan embodiment, if the destination IP address or destination URL includedin the header of the request packet is an IP address or URLpredetermined for a network information request, the FAFU 318 deliversthe request packet to the network information handler 322 instead of tothe CN 340. Communication for delivering a network information requestand a request result between the user application 302 of the mobileterminal 300 and the network information handler 322 is performedthrough an open interface, such as a web API like REST, or SDK.

In operation 510, the network information handler 322 provides networkinformation to the user application 302 of the mobile terminal 300through the BBU 312. For example, the network information may include atleast one of a weather of a region where an AN is located, a load of anAN and/or an access node, a backhaul bandwidth, and location informationat the request of the mobile terminal 300, and may be configured withone or more IP packets.

FIG. 6 illustrates a detailed structure of a FAFU according to anembodiment of the present disclosure.

Referring to FIG. 6, a FAFU 318 is illustrated, where the FAFU 318 islocated between a GTP processor 320 and a PDCP processor 316 and mayinclude a rule storing unit 602, a filtering unit 604, and a mappingunit 606.

A filtering rule 600 includes a 5-tuple of an IP, that is, a source IPaddress, a source port number, a destination IP address, a destinationport number, and a protocol type, and may be directly input by a BSoperator through a command line or may be set by a system manager (notshown) of an operator network. A system manager is a management nodethat provides an interface having an operator-matching function to allowthe operator to perform an operation and maintenance with respect to anaccess node, and also provides software management, configurationmanagement, performance management, and failure management.

Each filtering rule corresponds to each edge application and may beset/changed/deleted when each edge application isinstalled/updated/deleted in or from the access node. The system managerobtains information about a corresponding filtering rule when an edgeapplication is installed in an access node, and delivers the informationto the FAFU 318, which then stores the filtering rule corresponding tothe information in the rule storing unit 602 and generates the filteringrule and a tuple with a corresponding edge application.

The filtering unit 604 filters packets received from the GTP processor320, the PDCP processor 316, an edge application 334, or a networkinformation handler 322 according to the filtering rule stored in therule storing unit 602, and the mapping unit 606 determines acorresponding destination according to the filtering and transmits thepackets to an entity that is the determined destination. An example ofpacket filtering based on a destination is as described below.

For example, a DownLink (DL) packet received through the GTP processor320 may be transmitted directly to the PDCP processor 316 or deliveredto the corresponding edge application 334 through the mapping unit 606.In another example, an UpLink (UL) packet received through the PDCPprocessor 316 may be transmitted directly to the GTP processor 320 ordelivered to the corresponding edge application 334 or the networkinformation handler 322 through the mapping unit 606. In anotherexample, the packet received from the edge application 334 may betransmitted to the GTP processor 320 or delivered to the PDCP processor316. In another example, the packet received from the networkinformation handler 322 may be transmitted to the PDCP processor 316 ordelivered to the corresponding edge application 334.

The mapping unit 606 determines a tuple corresponding to the edgeapplication 334 when packets are delivered to the edge application 334from the FAFU 318, and determines whether to deliver packets receivedfrom the edge application 334 to the PDCP processor 316 or the GTPprocessor 320, based on a tuple of the received packets. To this end,the mapping unit 606 may use at least one of a bearer ID of a radiobearer used in packet delivery between an access node and a mobileterminal, a Tunneling Endpoint ID (TEID) used for GTP tunneling, asource P address/port number, a destination IP address/port number, andIP information for tunneling.

FIGS. 7 through 9 illustrate operations corresponding to servicescenarios according to various embodiments of the present disclosure.

Referring to FIG. 7, a system is illustrated, in which a publicapplication 704 is installed in an AS 702 located on the Internet or anexternal network. A UE 716 includes a user application 718, and connectsto an access node 710 by using a wireless access technique. The accessnode 710 includes an eNB block 712 configured with a modified existingBS platform and an edge application 714 according to an embodiment ofthe present disclosure, and may connect to the public application 704 ofthe AS 702 through a CN 706. The eNB block 712 includes a protocol stackaccording to an existing BS platform, for example, PHY, MAC, RLC, PDCP,GTP, and the like, and may also include an FAFU according to anembodiment of the present disclosure. The CN 706 may be configured, forexample, with an Evolved Packet Core (EPC) of an LTE system.

The user application 718 directly connects to a particular edgeapplication 714 of the access node 710, which is associated with adesired service, for example, a local weather or an advertisement, andreceives content or information regarding the desired service from theedge application 714, as indicated by 720. Access information regardingthe edge application 714, for example, a destination IP address or adestination URL may be provided to a user through an offlineadvertisement leaflet, a Television (TV), a medium, or the like, and theuser may directly input the destination IP address or the destinationURL by using an input means of the UE 716.

In another embodiment, the access node 710 provides prior information(such as an advertisement or the like) regarding a service that can beprovided through the edge application 714, to the UE 716 through a radiochannel, and the UE 716 displays a soft button or a menu key throughwhich the edge application 714 may be connected, on a display screen,and senses selection (a touch) of the soft button or the menu key fromthe user, thus triggering a service request for the edge application714. In another embodiment, a particular application installed in theuser or the UE may request and obtain access information regarding theedge application 704 by using a preset IP address or URL, and the usermay send a service request to the edge application by using the obtainedaccess information.

Referring to FIG. 8, a system is illustrated, in which a publicapplication 804 is installed in an AS 802 located on the Internet or anexternal network. A UE 816 includes a user application 818 and connectsto an access node 810 by using a wireless access technique. The accessnode 810 includes an eNB block 812 configured with a modified existingBS platform and an edge application 814 according to an embodiment ofthe present disclosure, and may connect to a public application 804 ofthe AS 802 through a CN 806.

If the user application 818 sends a service request for a desiredservice, for example, real-time gaming or online editing to the accessnode 810 and the access node 810 includes the edge application 814capable of processing the service request, then the access node 810filters the service request and delivers the service request to the edgeapplication 814. The edge application 814 provides content orinformation regarding the desired service to the user application 818according to the service request, as indicated by 822. When necessary,the edge application 814 may connect to the public application 804 torequest and receive additional information necessary for providing theservice, as indicated by 820.

Referring to FIG. 9, a system is illustrated, in which a publicapplication 904 is installed in an AS 902 located on the Internet or anexternal network. A UE 916 includes a user application 918 and connectsto an access node 910 by using a wireless access technique. The accessnode 910 includes an eNB block 912 configured with a modified existingBS platform and an edge application 914 according to an embodiment ofthe present disclosure, and may connect to a public application 904 ofthe AS 902 through a CN 906.

For example, if the edge application 914 provides a transparent cachingservice, the user application 918 sends a service request for desiredcontent to the access node 910 which then filters the service request,instead of delivering the service request to the public application 904,to deliver the service request to the edge application 914. If the edgeapplication 914 has not stored therein, the desired contentcorresponding to the service request, the edge application 914 sends theservice request for the content to the public application 904, asindicated by 920, receives the content from the public application 904through the CN 906 and stores (caches) the content, and provides thestored content to the user application 918, as indicated by 822. If theedge application 914 has stored the content therein, the edgeapplication 914 may directly provide the stored content to the userapplication 918 without accessing the public application 904.

According to various embodiments of the present disclosure operating asdescribed above, AN information such as a BS load, a backhaul bandwidth,location information, or the like is provided to a mobile terminal,thereby identifying an application service based on the AN informationand easily supporting different levels of Quality of Service (QoS).Moreover, various embodiments of the present disclosure facilitateaddition of value-added services or expansion to the value-addedservices, along with advances in characteristics and techniques ofmobile communication networks.

While the present disclosure has been shown and described with referenceto various embodiments thereof, it will be understood by those skilledin the art that various changes in form and details may be made thereinwithout departing from the spirit and scope of the present disclosure asdefined by the appended claims and their equivalents.

Various aspects of the present disclosure can also be embodied ascomputer readable code on a non-transitory computer readable recordingmedium. A non-transitory computer readable recording medium is any datastorage device that can store data which can be thereafter read by acomputer system. Examples of the non-transitory computer readablerecording medium include Read-Only Memory (ROM), Random-Access Memory(RAM), CD-ROMs, magnetic tapes, floppy disks, and optical data storagedevices. The non-transitory computer readable recording medium can alsobe distributed over network coupled computer systems so that thecomputer readable code is stored and executed in a distributed fashion.Also, functional programs, code, and code segments for accomplishing thepresent disclosure can be easily construed by programmers skilled in theart to which the present disclosure pertains.

At this point it should be noted that various embodiments of the presentdisclosure as described above typically involve the processing of inputdata and the generation of output data to some extent. This input dataprocessing and output data generation may be implemented in hardware orsoftware in combination with hardware. For example, specific electroniccomponents may be employed in a mobile device or similar or relatedcircuitry for implementing the functions associated with the variousembodiments of the present disclosure as described above. Alternatively,one or more processors operating in accordance with stored instructionsmay implement the functions associated with the various embodiments ofthe present disclosure as described above. If such is the case, it iswithin the scope of the present disclosure that such instructions may bestored on one or more non-transitory processor readable mediums.Examples of the processor readable mediums include Read-Only Memory(ROM), Random-Access Memory (RAM), CD-ROMs, magnetic tapes, floppydisks, and optical data storage devices. The processor readable mediumscan also be distributed over network coupled computer systems so thatthe instructions are stored and executed in a distributed fashion. Also,functional computer programs, instructions, and instruction segments foraccomplishing the present disclosure can be easily construed byprogrammers skilled in the art to which the present disclosure pertains.

1. A method for hosting an application by an access node which providesnetwork access to a terminal in a mobile communication system, themethod comprising: receiving a request packet for a service request froma user application of a mobile terminal; delivering the request packetto an application included in the access node, if a destination of therequest packet corresponds to the application of the access node;providing a service to the user application of the mobile terminalthrough the application; and delivering the request packet to acorresponding public application on an external network, if theapplication corresponding to the destination of the request packet doesnot exist in the access node.
 2. The method of claim 1, wherein theproviding of the service comprises: obtaining information of an accessnetwork in response to the request packet; and providing the obtainedinformation of the access network to the user application.
 3. The methodof claim 2, wherein the request packet is delivered, through a webApplication Program Interface (API) or an interface based on a SoftwareDevelopment Kit (SDK), to an information retrieving unit that collectsand manages information of the access network in the access node.
 4. Themethod of claim 1, further comprising filtering the request packet byusing information included in a header of the request packet.
 5. Themethod of claim 1, further comprising filtering the request packet byusing a destination Internet Protocol (IP) address included in a headerof the request packet.
 6. The method of claim 1, further comprisingfiltering the request packet by using a Universal Resource Locator (URL)included in a header of the request.
 7. The method of claim 1, whereinthe providing of the service comprises providing a cache service of thepublic application through the application included in the access node.8. An access node device which provides a network access to a terminaland provides application hosting in a mobile communication system, theaccess node device comprising: a forwarding unit configured to: identifya destination of a request packet, upon receiving the request packet fora service request from a user application of a mobile terminal; deliverthe request packet to an application included in the access node device,if a destination of the request packet corresponds to the application ofthe access node device; and deliver the request packet to acorresponding public application on an external network, if theapplication corresponding to the destination of the request packet doesnot exist in the access node device; and an application executing unitconfigured to provide a service to the user application of the mobileterminal through the application.
 9. The access node device of claim 8,wherein the forwarding unit is further configured to: obtain informationof an access network in response to the request packet; and provide theobtained information of the access network to the user application. 10.The access node device of claim 9, wherein the request packet isdelivered, through a web Application Program Interface (API) or aninterface based on a Software Development Kit (SDK), to an informationretrieving unit that collects and manages information of the accessnetwork in the access node device.
 11. The access node device of claim8, wherein the forwarding unit is further configured to filters therequest packet by using information included in a header of the requestpacket.
 12. The access node device of claim 8, wherein the forwardingunit is further configured to filters the request packet by using adestination Internet Protocol (IP) address included in a header of therequest packet.
 13. The access node device of claim 8, wherein theforwarding unit is further configured to filters the request packet byusing a Universal Resource Locator (URL) included in a header of therequest.
 14. The access node device of claim 8, wherein the applicationexecuting unit is further configured to provide a cache service of thepublic application through the application included in the access nodedevice.
 15. The access node device of claim 8, wherein the requestpacket is delivered to the application included in the access nodedevice by Internet Protocol (IP)-in-IP tunneling.
 16. The method ofclaim 1, wherein the request packet is delivered to the applicationincluded in the access node by Internet Protocol (IP)-in-IP tunneling.17. A non-transitory computer-readable storage medium storinginstructions that, when executed, cause at least one processor toperform the method of claim 1.